Designing configurable processor with hardware extension for instruction extension to replace searched slow block of instructions

ABSTRACT

A design apparatus for designing a configurable processor for an application, includes an analysis unit that analyzes the content of a program to be executed by the processor; a hardware extension unit that searches the program for a part of the program allowing hardware extension in accordance with the analysis results by the analysis unit and generates hardware extension information for the searched part; an extension instruction definition unit that searches the program for a part allowing use of an extension instruction in accordance with the analysis results by the analysis unit and generates definition of an extension instruction for the searched part; and a performance estimation unit that estimates whether or not the performance of the processor satisfies a target performance using at least one of the hardware extension information generated by the hardware extension unit and the definition of the extension instruction generated by the extension instruction definition unit.

CROSS REFERENCE TO RELATED APPLICATIONS AND INCORPORATION BY REFERRENCE

This application is based upon and claims the benefit of priority from prior Japanese Patent Application P2004-24499 filed on Jan. 30, 2004; the entire contents of which are incorporated by reference herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a design apparatus for a configurable processor for a target application, a design method for the same, and a library optimization method for the same. It particularly relates to a technique for automating extending hardware and defining extension instructions in a configurable-processor design phase.

2. Description of the Related Art

To design system LSIs such as the SoC (system on chip) in which a re-configurable processor capable of being added application-specific instructions is embedded, designers must design a source program for an algorithm to be used in a to-be-developed application system using a high level language such as C language and then carry out a high-level system simulation verifying whether or not a desired performance has been attained. If those verification results have not satisfied that desired performance, bottlenecks are then searched and identified. And an additionally extension instruction (user-defined instruction) is then defined, a region needing to be replaced with that extension instruction and/or a region needing to be replaced with specific hardware is selected, the present source program is re-written, and the system simulation is then carried out again, verifying whether or not that desired performance has been attained.

As a means to facilitate such series of operations, an apparatus that establishes a verification environment and a development tool (see Japanese Patent Application Laid-open No. 2002-230065) and an apparatus that aids a performance evaluation operation in the initial phase of an operation for distinguishing hardware sections from software sections (see Japanese Patent Application Laid-open No. 2000-57188), for example, are disclosed.

However, since most of the conventional operations for defining extension instructions, making a specification for an instruction set and selecting a source program region to be replaced with an extension instruction and/or a region to be replaced with specific hardware based on the analysis results, or related operations are manually carried out on a trial and error basis, those operations take a long time and a lot of work.

Moreover, since there are many selectable, extension instruction definition methods and extending methods including usage of extension instructions and specific hardware, finding an optimal definition method and an extending method therefrom requires verification of each method, which takes a very long time and a lot of work.

Furthermore, there is a problem with the conventional verification method of carrying out system simulation and verifying whether or not a desired performance has been attained. Particularly, since conventional analysis of a program-based operation is made based on the execution count for each source program function and execution count for each instruction, comprehensive judgment cannot be made. This is because the analysis based on each function merely allows rough analysis of the operation while the analysis based on each instruction loses the relationship between adjacent instructions.

Furthermore, there are no tools for automatically generating an extension instruction set that is newly defined by a user, which may be useful to run a source program.

Yet furthermore, even though the source program may be optimized using a newly defined, extension instruction, libraries to be used to compile the source program cannot be optimized.

SUMMARY OF THE INVENTION

A first aspect of the present invention inheres in a design apparatus for designing a configurable processor for an application, including: (A) an analysis unit that analyzes the content of a program to be executed by the processor; (B) a hardware extension unit that searches the program for a part allowing hardware extension in accordance with the analysis results by the analysis unit and generates hardware extension information for the searched part; (C) an extension instruction definition unit that searches the program for a part allowing use of an extension instruction in accordance with the analysis results by the analysis unit and generates definition of an extension instruction for the searched part; and (D) a performance estimation unit that estimates whether or not the performance of the processor satisfies a target performance using at least one of the hardware extension information generated by the hardware extension unit and the definition of the extension instruction generated by the extension instruction definition unit.

A second aspect of the present invention inheres in a configurable processor design apparatus, which includes an analysis unit that analyzes the content of a program to be executed by a configurable processor for an application and an extension instruction definition unit that searches the program for a part allowing use of an extension instruction in accordance with the analysis results by the analysis unit and generates definition of an extension instruction for the searched part; said configurable processor design apparatus comprising a library optimizer that optimizes a library used for compiling the program; wherein said library optimizer includes: (A) an analyzer that analyzes an instruction sequence for the processor suitable for an extension instruction defined in that definition; (B) a detection unit that determines based on the analysis results by the analyzer whether or not there is the instruction sequence in binary codes of the library; and (C) a binary conversion unit that optimizes the binary codes of the library in accordance with the determination results by the detection unit.

A third aspect of the present invention inheres in a computer-aided design method of designing a configurable processor for an application and satisfying a target performance for the processor, comprising: (A) analyzing the content of a program to be executed by the processor; (B) searching the program for a part allowing hardware extension in accordance with the analysis results and generating hardware extension information of the searched part; (C) searching the program for a part allowing use of an extension instruction in accordance with the analysis results and generating definition of an extension instruction for the searched part; and (D) estimating whether the performance of the processor satisfies a target performance when using at least one of the generated hardware extension information and the generated definition of the extension instruction.

A fourth aspect of the present invention inheres in a design method satisfying a target performance for the processor which is re-configurable for an application, the design method comprising: (A) inputting a program to be executed by the processor and analyzing the content of the inputted program; (B) searching the program for a part allowing hardware extension in accordance with the analysis results and generating hardware extension information of the searched part; (C) searching the program for a part allowing use of an extension instruction in accordance with the analysis results and generating definition of an extension instruction for the searched part; and (D) estimating based on at least one of the generated definition of the extension instruction and the generated hardware extension information whether or not the performance of the processor satisfies a target performance.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary configuration of a re-configurable processor design apparatus according to the first embodiment;

FIG. 2 is a flowchart exemplifying a design procedure by the design apparatus shown in FIG. 1;

FIG. 3 shows an exemplary procedure represented by pseudo-codes for extension instruction use and/or hardware extension;

FIG. 4 shows an exemplary layout of a display screen used to designate a target portion to be subjected to hardware extension and/or extension instruction use;

FIG. 5 exemplifies a configuration of a configurable processor designed using the design apparatus and the design method-according to the first embodiment;

FIG. 6 shows an exemplary configuration of an extension instruction definition unit according to the second embodiment;

FIG. 7 is a flowchart showing an exemplary operation of generating an extension instruction description by the extension instruction definition unit shown in FIG. 6;

FIG. 8 shows an exemplary source program, which is input to the extension instruction definition unit shown in FIG. 6;

FIG. 9 shows exemplary defined instructions for a coprocessor prior to extension instruction use;

FIG. 10 exemplifies assembly codes, which are the results of compiling the source program shown in FIG. 6;

FIG. 11 shows an exemplary defined extension instruction description generated by an instruction description generation unit;

FIG. 12 shows exemplary results of compiling the source program shown in FIG. 8 using a compiler after addition of extension instructions;

FIG. 13 shows an exemplary source program, which is input to the extension instruction definition unit shown in FIG. 6;

FIG. 14 shows exemplary assembly codes, which are the results of compiling the program shown in FIG. 13 using an instruction set without extension instructions;

FIG. 15 shows an exemplary defined extension instruction description generated by the instruction description generation unit;

FIG. 16 shows exemplary assembly codes, which are the results of compiling the program shown in FIG. 13 using extension instructions;

FIG. 17 shows an exemplary configuration of a dynamic analysis unit according to the third embodiment;

FIG. 18 shows an exemplary configuration of an instruction sequence division unit in the dynamic analysis unit shown in FIG. 17;

FIG. 19 shows an exemplary configuration of an instruction execution unit in the dynamic analysis unit shown in FIG. 17;

FIG. 20 shows an exemplary instruction sequence, which is input to the dynamic analysis unit shown in FIG. 17;

FIG. 21 shows exemplary branch convergence information output from a branch instruction search unit in the instruction sequence division unit shown in FIG. 17;

FIG. 22 shows exemplary results of sorting the branch convergence information shown in FIG. 21 in address order;

FIG. 23 shows exemplary instruction block information output from a branch block generation unit in the instruction sequence division unit shown in FIG. 18;

FIG. 24 shows an exemplary instruction block execution count output from an instruction block execution count calculation unit shown in FIG. 18;

FIG. 25 shows an exemplary configuration of a design apparatus according to the fourth embodiment (first example);

FIG. 26 shows an exemplary source program, which is input to the design apparatus shown in FIG. 25;

FIG. 27 shows an exemplary user-defined instruction group, which is input to the design apparatus shown in FIG. 25;

FIG. 28 shows exemplary results of compiling the program in FIG. 26 without using the user-defined instruction group shown in FIG. 27;

FIG. 29 shows exemplary results of compiling the program in FIG. 26 using the user-defined instruction group shown in FIG. 27;

FIG. 30 shows an example of an assembly code A<muldivi> derived from a user-defined instruction group U_I;

FIG. 31 shows an example of an assembly code A<muldiv2> derived from a user-defined instruction group U_(—)2;

FIG. 32 shows an exemplary defined instruction set output from an instruction set generation unit;

FIG. 33 shows an exemplary configuration of a design apparatus according to the fourth embodiment (third example);

FIG. 34 shows an exemplary source program, which is input to the design apparatus shown in FIG. 33;

FIG. 35 shows an exemplary user-defined instruction group, which is input to the design apparatus shown in FIG. 33;

FIG. 36 shows exemplary results of compiling the program shown in FIG. 34 using the user-defined instruction group shown in FIG. 35;

FIG. 37 shows an exemplary instruction block set divided by a program division unit;

FIG. 38 shows exemplary user-defined instructions and opcodes (including undefined codes);

FIG. 39 shows exemplary user-defined instructions and opcodes (already assigned codes);

FIG. 40 shows exemplary assembly codes wherein some thereof are replaced with defined instruction subsets;

FIG. 41 shows an exemplary configuration of a library optimizer according to the fifth embodiment;

FIG. 42 shows an exemplary detailed configuration of an analysis unit in the library optimizer shown in FIG. 41;

FIG. 43 shows an exemplary detailed configuration of a detection unit in the library optimizer shown in FIG. 41;

FIG. 44 shows an exemplary detailed configuration of a conversion unit in the library optimizer shown in FIG. 41;

FIG. 45 shows an exemplary function registered in a library optimized by the library optimizer shown in FIG. 41;

FIG. 46 shows an exemplary binary script for the function shown in FIG. 41;

FIG. 47 shows an exemplary extension instruction definition file, which is input to the library optimizer shown in FIG. 41;

FIG. 48 shows an exemplary assembler definition file and a C language header file, which are input to the library optimizer shown in FIG. 41 from the outside;

FIG. 49 shows exemplary library data converted by the library optimizer;

FIG. 50 shows exemplary codes shifted for filling the gap in the library data shown in FIG. 49; and

FIG. 51 shows exemplary ‘nop’ instructions filled in a new gap developed by the shifting process shown in FIG. 50.

DETAILED DESCRIPTION OF EMBODIMENTS

Various embodiments of the present invention will be described with reference to the accompanying drawings. It is to be noted that the same or similar reference numerals are applied to the same or similar parts and elements throughout the drawings, and the description of the same or similar parts and elements will be omitted or simplified.

In the following descriptions, numerous specific details are set forth such as specific instruction values, etc. to provide a thorough understanding of the present invention. However, it will be obvious to those skilled in the art that the present invention may be practiced without such specific details.

First Embodiment

As shown in FIG. 1, the design apparatus according to the first embodiment includes a tool generator 103, a language tool 104, a simulator 105, an extending unit 109, an input/display unit 114 and related units.

The tool generator 103 is a development environment generation tool for a re-targetable or configurable processor, which receives processor configuration information 102 and then generates, for example, the language tool 104, a library 112, and the simulator 105 using the inputted processor configuration information 102. The processor configuration information 102 includes information of definition of extension instructions and hardware extension information.

The language tool 104 has a compiler 121 and a static analysis unit 122. The compiler 121 inputs a program 101 written in a certain language such as C language and then compiles it into a simulator 105—executable module 106 (assembly language). The program 101 describes an entire algorithm or a part thereof to be executed by a to-be-designed processor. The static analysis unit 122 includes a parser, which parses a C language based program, and outputs as static analysis information 107, a syntactic tree, the data flow analysis results, the looping analysis results, and the variable's lifetime analysis results, for example.

The simulator 105 has a simulation unit 131 and a dynamic analysis unit 132. The simulation unit 131 carries out simulation of the executable module 106 generated by the language tool 104. The dynamic analysis unit 132 carries out profiling, namely, analyzing the execution information for each function, statement, and instruction, and then outputting the results as dynamic analysis information 108.

The extending unit 109 includes an extension instruction definition unit 141, a hardware extension unit 142, and a performance estimation unit 143. The extension instruction definition unit 141 searches the program 101 for a region needing to be exchanged with an extension instruction using the static analysis information 107 and the dynamic analysis information 108, and generates a definition of the extension instruction for that region. The hardware extension unit 142 searches the program 101 for a region needing to be subjected to hardware extension using the static analysis information 107 and the dynamic analysis information 108, and then generates hardware extension information for that region. The definitions of the extension instruction generated by the extension instruction definition unit 141 and the hardware extension information generated by the hardware extension unit 142 are reflected in the processor configuration information 102. When having carried out hardware extension, the result thereof is reflected in the program 101 (written in C). The performance estimation unit 143 estimates whether or not the performance of a target processor may reach a target performance using both or either of the definition of extension instructions generated by the extension instruction definition unit 141 and the hardware extension information generated by the hardware extension unit 142. In other words, the performance estimation unit 143 is given a target performance (a target function and a target value) with certain constraints 110, and searches the function space for a point satisfying that target value (which represents a combination of the hardware extension method and the definition of an extension instruction). The target function may be the execution speed for the program 101, for example.

The extension instruction definition unit 141 and the hardware extension unit 142 may be able to use externally provided constraints 110. The constraints 110 limit the search domain to be searched by the performance estimation unit 143. The constraints 110 may be for the number of gates, code size, and power consumption, for example.

FIG. 2 shows an exemplary procedure for designing certain software, which is executed by certain hardware or a processor including a configurable processor.

This example of the procedure for designing to be explained forthwith aims to provide a to-be-designed processor executing the program 101 at a speed of less than or equal to a predetermined reference value.

In step S201, an algorithm to be executed by a processor is written in C into the program 101, which is then input via the input/display unit 114. The processor configuration information 102 is then generated via the input/display unit 114. Moreover, the constraints 110 for limiting extension (hardware extension and use of extension instructions) and the target performance for a processor are generated via the input/display unit 114. These pieces of information may be generated using an editor or the like, or may be generated by inputting a value for each of necessary items while displaying those necessary items using GUI.

Next, in step S202, the tool generator 103 generates (customizes) the language tool 104 and the simulator 105 in accordance with the processor configuration information 102. The compiler 121 in the generated language tool 104 compiles the program 101, converting it to the executable module 106. The static analysis unit 122 in the language tool 104 outputs static analysis information 107 using syntax analysis information obtained from the program 101 compiled results. The dynamic analysis unit 132 uses an assembly language program and/or program analysis information generated as the static analysis information 107 by the compiler 121. The program analysis information includes loop information with the number of looping nests for each of statements comprising a C language based program, the number of instructions comprising each function, and the size of external data and codes that each function uses, for example.

The simulation unit 131 carries out simulation using the executable module 106 generated by the language tool 104, and the dynamic analysis unit 132 then analyzes the simulation execution results, outputting dynamic analysis information 108. The dynamic analysis unit 132 uses the profile information generated by the simulation unit 131 as the dynamic analysis information 108. More specifically, the profile information such as the count of calling each function, each statement execution count and each instruction execution count, and a ratio of the instruction execution count for each function to instruction execution count for the entire program 101 is output.

Next, in step S203, the performance estimation unit 143 in the extending unit 109 carries out evaluation using the static analysis information 107 and the dynamic analysis information 108. The dynamic analysis information 108 includes an executed instruction count and the number of executed cycles, for example. A program 101 processor execution speed is estimated using these pieces of information. In step S204, whether or not the program 101 processor execution speed has reached a predetermined target performance, which is given in the constraints 110, is determined. In the case of a code size being given in the constraints 110, it is compared with a code size included in the static analysis information 107, which allows determination of whether or not the constraints 110 are satisfied.

If the estimated execution speed satisfies the predetermined target performance, and the constraints 110 are also satisfied, this program proceeds to semiconductor fabrication steps beginning with step S211.

Otherwise, if the estimated execution speed does not satisfy the predetermined target performance, and the constraints 110 are also not satisfied, this program proceeds to step S205 in which the extension instruction definition unit 141 and the hardware extension unit 142 carry out use of extension instructions and hardware extension, thereby changing the processor architecture so that the constraints 110 and the target performance can be satisfied. More specifically, multiple instructions in the program 101, for example, are represented by an additional, newly defined single instruction, the defined single instruction is used in the program 101 (extension instruction use), and/or a partial software process in the program 101 is replaced with a dedicated hardware (hardware extension), thereby improving the execution speed of the entire processor. Since this hardware extension is carried out for a certain organized process (e.g., a function), a further improved performance than that in the case of extension instruction use may be provided.

That extension processing by the extending unit 109 can be regarded as dealing with an optimal extension method search problem of searching for an optimal extension method from a variety of methods for use of extension instructions and hardware extension. In the following, the case of searching using the static analysis information 107 and the case of searching using the dynamic analysis information 108 are described. A variety of algorithms for solving such search problem have been proposed, and the so-called Greedy algorithm is selected from them herein.

First, the case of using the static analysis information 107 is detailed. FIG. 3 shows an extending procedure represented by pseudo-codes. Processing from lines 0303 and 0313 in FIG. 3 identifies a bottleneck function in the program 101 (i.e., a function including the greatest number of instructions) using the static analysis information 107, and then selects an extension method satisfying the constraints 110 and a target performance for the identified function. Similarly, processing from lines 0314 and 0323 identifies a bottleneck statement in the program 101 (i.e., a statement including the greatest number-of instructions) using the static analysis information 107, and then selects an extension method satisfying the constraints 110 and the target performance for the identified statement.

Replacement of a software process in the program 101 with dedicated hardware leads to increase in the number of gates, and the degree of increase in the number of gates may be evaluated using a high-level synthesis tool. When the number of gates is given as the constraints 110, usage of this information allows determination of whether or not the constraints 110 are satisfied. For a function to reference external data, that data needs to be transferred to a dedicated hardware before the referencing starts and transferred to a processor after the referencing ends. When selecting a function, consideration of that information allows an exact evaluation of the processor performance.

To search for an optimal extension method using the dynamic analysis information 108, the simulator 105 references the profiling results obtained by carrying out simulation. This allows acquisition of the ratio of the number of executed instructions in each function of the program 101 to number of executed instructions in the entire program 101. Functions with high ratios can be candidates for hardware extension or extension instruction use. Note that usage of both the static analysis information 107 and the dynamic analysis information 108 allows search for an optimal extension method. Moreover, in addition to automating the identification process for a target region to be subjected to hardware extension or extension instruction use, a user may designate a target region via the input/display unit 114.

If the determination process in step S204 determines that both the constraints 110 and the target performance have been satisfied, this procedure proceeds to the semiconductor fabrication steps beginning with step S211.

In step S211, mask data for a semiconductor circuit including a designed processor is generated using the results of designing in steps S201 to S205. In step. S212, masks are made based on the mask data generated in step S211. In step S213, a semiconductor circuit pattern including the above-mentioned processor is formed in and on a semiconductor substrate using the masks made in step S211.

FIG. 4 shows an exemplary display screen used for designating a target region to be subjected to hardware extension or extension instruction use via the input/display unit 114.

On the left side of the screen, a function display window 401 displaying functions comprising the program 101 is deployed such that calling relationships among functions can be understood. On the right side of the screen, a code display window 402 displaying function codes is deployed.

There are the following five types of operations for the function display window 401.

A first type of operation is to select a target function to be subjected to hardware extension. Multiple functions may be selected through this operation. According to the example shown in FIG. 4, a function ‘foo200( )’ is selected. The function selected through this first operation is a priority target to be subjected to hardware extension.

A second type of operation is to select a function not to be subjected to hardware extension. Multiple functions may be selected through this operation. The functions selected through this operation are not targets to be subjected to hardware extension.

A third type of operation is to select a target function to be subjected to extension instruction use. Multiple functions may be selected through this operation. The function selected through this operation is a priority target to be subjected to extension instruction use.

A fourth type of operation is to select a function not to be subjected to extension instruction use. Multiple functions may be selected through this operation. The functions selected through this operation are not targets to be subjected to extension instruction use.

A fifth type of operation is to select a function in which codes are to be displayed in the code display window 402. According to the example shown in FIG. 4, codes in the function ‘foo200( )’ selected in the function display window are displayed.

There are two types of operations for the code display window 402.

A first type of operation is to designate a target code region to be subjected to extension instruction use. Multiple regions may be designated through this operation. The region designated through this operation is a priority target to be subjected to extension instruction use.

A second type of operation is to designate a code region not to be subjected to extension instruction use. Multiple regions may be designated through this operation. The regions designated through this operation are not subjected to extension instruction use.

FIG. 5 shows an exemplary configuration of a configurable processor 500 designed using a design apparatus and a design method according to this embodiment. The configurable processor 500 includes a timer/counter 501, an interrupt controller 502, a debugger 503, optional instructions 504, a configurable processor core 505, a bus interface unit (BIU) 506, local memory including instruction cache RAM 508 and data cache RAM 509, a global bus interface unit 510, a DSP unit 511, a user customized instruction (UCI) unit 512, a coprocessor 513, a hardware engine 514, and a data streamer 515 including a local bus 516 and a DMA controller 517. With the design apparatus and the design method according to the first embodiment, the optional instructions 504, the DSP unit 511, the UCI unit 512, the coprocessor core 505, the hardware engine 514 or related units become targets for extension, and the configurable processor 500 is extended to execute at an enhanced speed while compensating the performance of the configurable processor core 505.

As is described above, since the design apparatus and the design method of the first embodiment allow automatic definition of extension instructions, automatic extension of hardware, and automatic selection of an extension instruction, evaluation of a variety of extension methods can be made within a short time, which allows selection of an optimal extension method.

Second Embodiment

This second embodiment section describes how the extending unit 109 in the design apparatus shown in FIG. 1, more specifically, the extension instruction definition unit 141 determines whether or not extension instruction use target blocks in the program 101 can be surely subjected to extension instruction use, and if yes, how it generates a sequence of multiple instructions that define an equivalent extension instruction.

In addition to a predetermined instruction set, the configurable processor allows users to define application-specific extension instructions. Replacement of a bottleneck region in the program 101 with a smaller number of extension instructions particularly allows improvement in performance and code size. Therefore, that replacement is very effective. However, since in reality, there are constraints such as a limited number of registers capable of being used for operands and a limited number of arithmetic logic units, replacing a part of a program as is with an extension instruction is seldom. Therefore, users have to change the configuration of the program by trial and error, and find an extension instruction possible for replacement. This is time-consuming work for the users.

To solve this problem, as shown in FIG. 6, the extension instruction definition unit 141 according to the second embodiment includes an extension instruction use determination unit 602, which determines whether or not it is possible to generate an extension instruction for a process equivalent to a process for a extension instruction use target block in the program 101 (wherein that target block is designated based on block information 601), and an instruction description generation unit 604, which generates an extension instruction description 605 for a process equivalent to a process for the target block in response to the determination results by the extension instruction use determination unit 602. The extension instruction definition unit 141 includes a block division unit 603, which divides that target block. The instruction description generation unit 604 generates the extension instruction description 605 for part or all of each sub-block divided by the block division unit 603.

Note that the block division unit 603 is also capable of dividing a single statement in the program 101 into multiple blocks. The instruction description generation unit 604 is also capable of generating the extension instruction description 605 for a statement employing a predetermined variable or a block of the blocks generated by being divided that includes an instruction sequence employing a predetermined register. Moreover, the instruction description generation unit 604 is also capable of generating the extension instruction description 605, which defines a transfer instruction for transferring between a processor and an external register of the processor to which a variable used in a block is assigned.

FIG. 7 shows an exemplary process of generating the extension instruction description 605 carried out by the extension instruction definition unit 141.

Note that the following example represents a case of a block of statements from lines 0811 to 0814 in a program shown in FIG. 8 being designated as a target block and also coprocessor extension being selected and designated from several types of prepared instruction extension methods (these instruction extension methods are designated in the constraints 110). Criteria for determining whether extension instruction use is possible depend on the selected instruction extension method. Criteria for determining whether extension instruction use for coprocessor extension is possible are described in a section describing an extension instruction use determination process. It is assumed here that the coprocessor 513 having instructions given as an example in FIG. 9 is already attached.

‘_cop’ in line 0803 of FIG. 8 is a designator, which designates the compiler 121 to assign declared variables attached with that designator to registers of the coprocessor 513. FIG. 10 shows assembly codes resulting from compiling the source program of FIG. 8.

In step S701, the extension instruction use determination unit 602 determines whether or not an extension instruction for an extension instruction use target block can be generated. If the determination results (in step S702) reveal that generation of an extension instruction is possible, in step S703, the instruction description generation unit 604 generates the extension instruction description 605 for carrying out a process equivalent to a process for an extension instruction use target block.

It is assumed here that the constraints 110 for coprocessor extension include a limited number of definable operands in each extension instruction being three at the maximum, and a limited number of definable operands for general purpose registers of the processor core 505 being two at the maximum. Since the target block needs at least four registers of the core for operands, the extension instruction use determination unit 602 determines that it is impossible to use an extension instruction for that block.

Next, in step S704, the block division unit 603 divides the present block and tries to use an extension instruction. The block division unit 603 divides such that each statement in the block of lines 0811 to 0814 can comprise a block, and then tries to use an extension instruction for each divided block through a looping process from step S705 to step S709.

Since each of statements 0811 to 0813 in FIG. 8 are converted to a single instruction as shown in lines 1001 to 1003, the extension instruction use determination unit 602 determines in step S706 that each of them do not need to use an extension instruction. On the other hand, since the statement in line 0814 of FIG. 8 is converted to three consecutive instructions in lines 1004 to 1006 of FIG. 10, the extension instruction use determination unit 602 determines whether or not the constraints 110 for coprocessor extension are satisfied. A command statement in line 0814 of FIG. 8 inputs two values in respective registers of the processor core 505, the value in the register of the coprocessor 513, and a constant value, and then returns the corresponding result to the register of the processor core 505. Embedding the constant value somewhere within the operation for the instruction in place of an immediate addressing operand allows definition of that instruction having two processor core 505 register operands and a single coprocessor 513 register operand, thereby satisfying the constraints 110 for coprocessor extension. Therefore, the extension instruction use determination unit 602 determines that the command statement in line 0814 can use an extension instruction.

In step S708, as exemplified in FIG. 11, the instruction description generation unit 604 generates an extension instruction definition script 605 for the command statement in line 0814. The name of the extension instruction is ‘cinst_’ plus a number at the end for the extension instruction (e.g., ‘0001’ in the case of the example in FIG. 11), avoiding conflict with already defined instructions. Arguments in line 1101 are for variables that appear in line 0814 of FIG. 8. The behavior definition field in line 1103 is filled with the statement itself in line 0814 of FIG. 8. Note that instruction names and opcodes may be designated via the input/display unit 114.

Usage of ‘An Optimization Method Used by Compiler’ described later and giving an instruction description definition shown in FIG. 11 to the compiler (e.g., compiler 121) allows customization of the compiler to allow generation of coprocessor instructions defined in FIG. 8. The statement in line 0814 of FIG. 8 is compiled by the compiler after addition of extension instructions, into the compilation results shown in line 1204 of FIG. 12. The codes shown in FIG. 12 reduce by two instructions as compared with the number of codes in FIG. 10, which means that it is effective to decrease the code size, the number of executable instructions, and the number of execution cycles. Moreover, it is expected that application of such operation to many places of a source program may provide further improved results. Furthermore, conventionally, such an instruction addition procedure has been manually conducted; however, since it is automatically conducted using this system according to the present invention, development periods can be significantly reduced. Note that dividing blocks is conducted for every statement with those examples explained here; however, the unit of division may be every group of multiple statements or every partial section of a statement, and is defined through syntax tree analysis. Furthermore, this invention is explained by exemplifying the C language program; however, other computer languages such as an assembly language or a binary script may be used as well. When processing an assembly language program or a binary language program, the block division process should divide an instruction sequence. The behavior section in an instruction description written in an assembly language or a binary language should be generated as a script written in C or another language equivalent to an instruction sequence using an extension instruction.

Furthermore, according to the aforementioned description, the extension instruction use determination unit 602 has an existence of an instruction with an equivalent number of operands as a condition for determining whether extension instruction use is possible; however, the condition may further include a type of operation, types of statements appearing in a block or the like. For example, an instruction extension method capable of defining only instructions, each spending a single machine cycle while being executed, may determine that a multiplication instruction in a block cannot be processed. In addition, if a memory access statement or a control statement such as a function call statement exists in a block, the block cannot be processed either.

The flowchart of FIG. 7 shows the case of only a single extension instruction use target block being designated; alternatively, multiple extension instruction use target blocks may be subjected to repetitive execution of the process in FIG. 7, generating the extension instruction description 605 for those multiple target blocks. Moreover, according to the flowchart of FIG. 7, if any divided block is not available for extension instruction use, the procedure proceeds to the next step S710; alternatively, if it is determined that extension instruction use is impossible even by preparing several divided patterns, the procedure may still proceed to the next step S710. Furthermore, to control excessive increase in additional instructions, whether or not to carry out extension instruction use may be designated by a user via the input/display unit 114.

Next, the case of assigning variables to external registers of the processor is explained.

It is assumed here that a statement in line 1306 of FIG. 13 is provided as an extension instruction use target block. Note that the assembly codes, which result from compiling the program shown in FIG. 13 using an instruction set without extension instructions, are shown in FIG. 14. The assembly codes corresponding to the statement in line 1306 of FIG. 13 are shown in lines 1404 to 1405.

As shown in the flowchart of FIG. 7, in step S701, the extension instruction use determination unit 602 determines whether the statement in line 1306 of FIG. 13 can be subjected to extension instruction use. When the condition of limiting extension instructions is that up to two operands can be used for general purpose registers of the processor core 505, the statement in line 1306 takes three registers corresponding to variables ‘tmp’, ‘a[i]’, and ‘x[i]’. Therefore, the extension instruction use determination unit 602 determines in step S702 that extension instruction use is impossible.

Next, in step S703, the block division unit 603 tries to resolve the statement in line 1306. The block division unit 603 conducts syntax tree analysis for the statement in line 1306, resolving it into two blocks: ‘Z=(a[i]+x[i])/2’ and ‘tmp=tmp+Z’. Note that the variable ‘Z’ is an intermediate variable developed by resolving the statement.

In step S706, the extension instruction use determination unit 602 determines whether or not those two blocks can be subjected to extension instruction use. Since it is not determined whether the intermediate variable ‘Z’ can share a register assigned for either ‘a[i]’ or ‘x[i]’ in the block of ‘Z=(a[i]+x[i])/2’, three register operands are needed. Therefore, the extension instruction use determination unit 602 determines that the block of ‘Z=(a[i]+x[i])/2’ cannot be subjected to extension instruction use. On the other hand, since the block of ‘tmp=tmp+Z’ is converted to a single instruction, the extension instruction use determination unit 602 determines that that block cannot be subjected to extension instruction use. And even if the statement ‘Z=(a[i]+x[i])/2’ were to be further divided, it could only be divided into a block, which can be converted to a single instruction. Therefore, the procedure proceeds to extension instruction use determination step S710, which considers assignment of variables to external registers of the processor.

It is assumed here that data types of variables and other attributes thereof appearing in each statement shown in FIG. 13 are already known. Acquisition of this information can be made through a well-known program analysis technique, and the program analysis results may be provided externally, or a program analysis function may be included.

With this embodiment, variables suitable for being assigned to external registers are chosen from the variables in a block, and the variable ‘tmp’ is assumed to be assigned to an external register because it is a basic data type local variable. As a result, the number of the registers of the core for line 1306 is only two corresponding to variables ‘a[i]’ and ‘x[i]’. Therefore, in step S711, the extension instruction use determination unit 602 determines that extension instruction use is possible.

In step S712, since the instruction description generation unit 604 assigns to an external register the variable as well as the instruction corresponding to the block in line 1306, an instruction for data transfer between the extended module registers and the processor general purpose registers is automatically, additionally generated. As a result, the instruction description generation unit 604 generates an instruction definition script 605, which defines three instructions as exemplified in FIG. 15. A variable ‘dspreg’ appearing in the behavior section of the instruction definition script 605 exemplified in FIG. 15 is a variable representing a register in the extended module, and is defined as ‘reg: 32: dspreg;’. The instruction ‘dspst’ is a transfer command for transferring from the processor registers to the extended module registers, while the instruction ‘dspld’ is a transfer command for transferring from the extended module registers to the processor registers. ‘dspreg’ in place of the variable ‘tmp’ assigned to an external register is used in the behavior section of the instruction ‘dinst_(—)0001’ generated from the statement in line 1306.

At this time, usage of ‘An Optimization Method Used by Compiler’ described later and provision of an instruction description definition to a compiler (compiler 121) allows customization of the compiler, providing the results of compiling the statement in line 1306 of FIG. 13 as shown in FIG. 16. Moreover, since the variable ‘tmp’ is assigned to a register in the extended module, the compiler generates in a place which substitutes for the variable ‘tmp’ and references the same, a transfer command for transferring to a register in the extended module. As a result, a transfer command for transferring from/to registers in the extended module is inserted before and after a loop; however, since the number of instructions in the loop decreases, both the number of executed instructions and the number of execution cycles decrease, and thus performance enhances.

(An Optimization Method Used by Compiler)

The aforementioned ‘An Optimization Method Used by Compiler’ is described forthwith.

When a user-defined extension instruction and definition of the behavior thereof are provided to the compiler (compiler 121), the compiler optimizes one of the instructions described in the program 101 for carrying out the same operation as that of an extension instruction defined by a user, into a machine language script corresponding to the user-defined extension instruction. More specifically, when carrying out a syntax analysis for the program 101, the compiler analyzes whether the instructions in the program 101 complies with the grammatical rules for instructions in the program 101, also analyzes whether a combination of instructions defines the extension instructions and the behaviors thereof, and then stores the definitions for the syntax-analyzed extension instructions and the behaviors thereof. Afterwards, the compiler determines whether or not the machine language scripts generated from a source program correspond to the behaviors of the stored, extension instructions; if yes, the compiler optimizes the machine language scripts into optimized machine language scripts corresponding to the behaviors of the extension instructions.

In this manner, the compiler 121 is capable of optimizing the compilation process for the program 101 using extension instructions defined by a user.

As has been detailed thus far, the second embodiment allows effective and easy definition of additional instructions, which used to be time-consuming and troublesome. Moreover, since the compiler is capable of automatically handling those additional instructions, the code size can be reduced and performance can be improved promptly.

Moreover, since the compiler is capable of block division, register assignment and the like, generation of various patterns of intra-block additional instructions can be made, and effectively searching for an extension instruction that has been conventionally searched by trial and error by a user is possible.

Third Embodiment

When dynamically analyzing the behavior of the program 101 based upon the simulation results, more specifically, analyzing each function execution count, for example, the dynamic analysis unit 132 can merely analyze the behavior roughly and cannot determine whether or not a certain sequence of consecutive instructions operate properly under a certain operating condition. In addition, analysis of each instruction execution count brings about losing the before and after relationship of each instruction, thereby making it impossible to judge with perspective. Therefore, with the third embodiment, an example of the behavior of the dynamic analysis unit 132 dividing an instruction sequence into basic blocks, which do not include branch instructions and do not converge, and then analyzing each basic block execution count is described.

FIG. 17 shows an exemplary configuration of the dynamic analysis unit 132 according to the third embodiment. An instruction sequence division unit 1703 receives an instruction sequence 1701 in an execution module 106 generated by the compiler 121 (compiler or assembler) and user designation division information 1702, which is information of an instruction block that a user desires to analyze the behavior (e.g., obtain an execution count), divides the instruction sequence 1701 within the range of the user designation division information 1702 into a block, and then outputs instruction block information 1704. The instruction sequence 1701 is generally called ‘object codes’ or ‘execution codes’. The user designation division information 1702 is information of a range of the instruction sequence 1701 to be subjected to behavior analysis that a user has designated, and is made up of a code start address and an end address. Note that the user designation division information 1702 is unessential that the instruction sequence division unit 1703 executes block division within a predetermined range as long as the user designation division information 1702 is not designated.

An instruction execution unit 1705 analyzes each instruction block execution count using the instruction block information 1704 output by the instruction sequence division unit 1703, and then outputs the analysis results as an instruction block execution count 1706, which will be dynamic analysis information 108.

FIG. 18 exemplifies a detailed structure of the instruction sequence division unit 1703. A branch instruction searching unit 1801 inputs the user designation division information 1702, and then defines the division range designated by a user as a search range. The branch instruction searching unit 1801 stores the start address for the instruction sequence 1701 as an initial value of a destination branch address for branch convergence information 1802.

Afterwards, the branch instruction searching unit 1801 searches the instruction sequence within the search range for all instructions possibly developing branches, and then stores as the branch convergence information 1802, an address for the searched branch instruction and a destination branch address, and information of whether the address is either for the branch instruction or for the branch destination. Since there are more than two destination branch addresses for conditional branch instructions, the branch instruction searching unit 1801 stores all of those addresses in the branch convergence information 1802.

Next, a branch block generation unit 1803 outputs the user designation division information 1702 as instruction block information 1704, sorts the branch convergence information 1802 according to address order, and then adds to the instruction block information 1704 the combination of before and after the sorted branch convergence information 1802 as an instruction block. Note that if the end address is a destination branch address when converting the branch convergence information 1802 to the instruction block information 1704, the value of the address is decreased by one. At this time, if the start address is a branch address, an instruction block is not added to the branch convergence information 1802.

FIG. 19 exemplifies a detailed configuration of the instruction execution unit 1705. An instruction block execution count is calculated using a present instruction and a present address kept by an instruction simulator 1906. Every time the instruction simulator 1906 executes a single instruction, the following operation is carried out.

Firstly, the instruction execution unit 1705 makes preliminary instruction information 1901 be nil before starting simulation. At the time of simulation, a block information calculation unit 1902 calculates and finds an instruction block to which the present instruction belongs, using the present address and the instruction block information 1704, and then stores the calculation results as block information 1903.

Afterwards, an information comparison unit 1904 inputs the preliminary instruction information 1901 and the block information 1903, and then determines whether or not to calculate the instruction block execution count 1706. If the output of the information comparison unit 1904 is different from that for the instruction block having the preliminary instruction information 1901 as the block information 1903, or if the instruction in the preliminary instruction information 1901 is a branch instruction, logical true is returned; otherwise, if not, logical false is returned.

An instruction block execution count calculation unit 1905 increments by one the execution count for a block corresponding to the block information 1903 only if the output of the information comparison unit 1904 is logical true. Lastly, the instruction block execution count calculation unit 1905 registers the present instruction and the block information 1903 as the preliminary instruction information 1901 irrelevant to the output value of the information comparison unit 1904.

The operation of the dynamic analysis unit 132 according to the third embodiment is explained forthwith using a specific example. Note that the user designation division information 1702 is not designated in the example described below.

FIG. 20 shows an example of the instruction sequence 1701 that the dynamic analysis unit 132 receives. The instruction sequence 1701 is made up of a combination of address information and an instruction. In reality, the instruction sequence 1701 is binary notation codes; however, for simplicity of explanation, the instructions are represented by mnemonic codes. According to the third embodiment, an instruction sequence 1701 including five types of instructions: ‘LD’, ‘ADD’, ‘SUB’, ‘JNZ’, and ‘JMP’ is prepared. Variables starting with ‘R’ in mnemonic notation denote registers, while numeric values surrounded with ‘( )’ denote memory access. The instruction ‘LD’ denotes load and store; ‘ADD’ denotes addition; ‘SUB’ denotes subtraction; ‘JNZ’ denotes branch if not zero; and ‘JMP’ denotes unconditional jump.

Firstly, when the instruction sequence division unit 1703 has inputted the instruction sequence 1701 shown in FIG. 20, the branch instruction searching unit 1801 stores the start address ‘0001’ for the instruction sequence 1701 with an attribute of ‘branch destination’ in the branch convergence information 1802. The branch instruction searching unit 1801 then searches the instruction sequence 1701 for a branch instruction. In the instruction sequence 1701, a branch instruction exists in addresses: ‘0006’, ‘0009’, and ‘000d’; wherein the branch instruction in the address ‘0006’ is a conditional branch instruction, and if the condition is satisfied, branching to an address of ‘000a’ is carried out. Otherwise, if not, the instruction in an address ‘0007’ is executed. The branch instruction searching unit 1801 registers the address ‘0006’ with an attribute of ‘branch’ and the addresses ‘000a’ and ‘0007’ with an attribute of ‘branch destination’in the branch convergence information 1802. Repetition of the same operations described above provides the branch convergence information 1802 as shown in FIG. 21. Lastly, the branch instruction searching unit 1801 sorts the branch convergence information 1802 according to address order, generating sorted branch convergence information 1802 as shown in FIG. 22.

Afterwards, a branch block generation unit 1803 inputs the branch convergence information 1802 generated as shown in FIG. 22, and then generates instruction block information 1704. The branch block generation unit 1803 reads out two consecutive pieces of information starting at the top address of the branch convergence information 1802. Pieces of information from addresses ‘0001’ (branch destination) and ‘0002’ (branch destination), which are a start address and an end address for the block information 1704, respectively, are read out first. In the case of using information with an attribute of ‘branch destination’ for the end address, that address is decreased by one. As a result, pieces of information such as a start address of ‘0001’ and an end address of ‘0001’ are obtained. The branch block generation unit 1803 registers those pieces of information in the instruction block information 1704.

Since information read out next from the branch convergence information 1802 is a combination of the addresses ‘0002’ (branch destination) and ‘0006’ (branch), the branch block generation unit 1803 registers information such as a start address of ‘0002’ and an end address of ‘0006’ in the instruction block information 1704.

Information read out next from the branch convergence information 1802 is a combination of the addresses ‘0006’ (branch) and ‘0007’ (branch destination); however, since an address with an attribute of ‘branch’ is not used as a start address, no operation is carried out with this combination.

Information read out next from the branch convergence information 1802 is a combination of the addresses ‘0007’ (branch destination) and ‘0009’ (branch). Proceeding as such results in provision of the instruction block information 1704 as shown in FIG. 23. Note that the instruction block information 1704 has an instruction block number attached to each block for identification.

Lastly, the instruction execution unit 1705 carries out simulation for instructions, and then calculates the instruction block execution count 1706. The first ten instructions are detailed below. It is assumed that the condition for the conditional branch instruction in the address ‘0006’ is satisfied and jumps to an address ‘000a’.

(1) Regarding address ‘0001’: the block information calculation unit 1902 calculates and finds that the instruction in the address ‘0001’ belongs to a block with an instruction block number ‘0’. The determination results of the information comparison unit 1904 say ‘no match’ because the preliminary instruction information 1901 is nil. The instruction block execution count calculation unit 1905 adds one to the execution count for the instruction block number ‘0’, and then registers the present instruction ‘LD’ and the instruction block number ‘0’ in the preliminary instruction information 1901. (2) Regarding address ‘0002’: the block information calculation unit 1902 calculates and finds that the instruction in the address ‘0002’ belongs to a block with an instruction block number ‘1’. The determination results of the information comparison unit 1904 say ‘no match’ because the contents of the preliminary instruction information 1901 are an instruction ‘LD’ and an instruction block number ‘0’. The instruction block execution count calculation unit 1905 adds one to the execution count for the instruction block number ‘1’, and then registers the present instruction ‘LD’ and the instruction block number ‘1’ in the preliminary instruction information 1901. (3) Regarding address ‘0003’: the block information calculation unit 1902 calculates and finds that the instruction in the address ‘0003’ belongs to a block with an instruction block number ‘1’. The determination results of the information comparison unit 1904 say ‘match’ because the contents of the preliminary instruction information 1901 are an instruction ‘LD’ and an instruction block number ‘1’. The instruction block execution count calculation unit 1905 does not calculate the execution count, but registers the present instruction ‘LD’ and the instruction block number ‘1’ in the preliminary instruction information 1901. (4) Regarding address ‘0004’: the block information calculation unit 1902 calculates and finds that the instruction in the address ‘0004’ belongs to a block with an instruction block number ‘1’. The determination results of the information comparison unit 1904 say ‘match’ because the contents of the preliminary instruction information 1901 are an instruction ‘LD’ and an instruction block number ‘1’. The instruction block execution count calculation unit 1905 does not calculate the execution count, but registers the present instruction ‘ADD’ and the instruction block number ‘1’ in the preliminary instruction information 1901. (5) Regarding address ‘0005’: the block information calculation unit 1902 calculates and finds that the instruction in the address ‘0005’ belongs to a block with an instruction block number ‘1’. The determination results of the information comparison unit 1904 say ‘match’ because the contents of the preliminary instruction information 1901 are an instruction ‘ADD’ and an instruction block number ‘1’. The instruction block execution count calculation unit 1905 does not calculate the execution count, but registers the present instruction ‘LD’ and the instruction block number ‘1’ in the preliminary instruction information 1901. (6) Regarding address ‘0006’: the block information calculation unit 1902 calculates and finds that the instruction in the address ‘0006’ belongs to a block with an instruction block number ‘1’. The determination results of the information comparison unit 1904 say ‘match’ because the contents of the preliminary instruction information 1901 are an instruction ‘LD’ and an instruction block number ‘1’. The instruction block execution count calculation unit 1905 does not calculate the execution count, but registers the present instruction ‘JNZ’ and the instruction block number ‘1’ in the preliminary instruction information 1901. (7) Regarding address ‘000a’: the block information calculation unit 1902 calculates and finds that the instruction in an address ‘000a’ belongs to a block with an instruction block number ‘3’. The determination results of the information comparison unit 1904 say ‘no match’ because the contents of the preliminary instruction information 1901 are an instruction ‘JNZ’ and an instruction block number ‘1’. The instruction block execution count calculation unit 1905 adds one to the execution count for the instruction block number ‘3’, and then registers the present instruction ‘SUB’ and the instruction block number ‘3’ in the preliminary instruction information 1901. (8) Regarding address ‘000b’: the block information calculation unit 1902 calculates and finds that the instruction in an address ‘000b’ belongs to a block with an instruction block number ‘4’. The determination results of the information comparison unit 1904 say ‘no match’ because the contents of the preliminary instruction information 1901 are an instruction ‘SUB’ and an instruction block number ‘3’. The instruction block execution count calculation unit 1905 adds one to the execution count for the instruction block number ‘4’, and then registers the present instruction ‘LD’ and the instruction block number ‘4’ in the preliminary instruction information 1901. (9) Regarding address ‘000c’: the block information calculation unit 1902 calculates and finds that the instruction in an address ‘000c’ belongs to a block with an instruction block number ‘4’. The determination results of the information comparison unit 1904 say ‘match’ because the contents of the preliminary instruction information 1901 are an instruction ‘LD’ and an instruction block number ‘4’. The instruction block execution count calculation unit 1905 does not calculate the execution count, but registers the present instruction ‘SUB’ and the instruction block number ‘4’ in the preliminary instruction information 1901. (10) Regarding address ‘000d’: the block information calculation unit 1902 calculates and finds that the instruction in an address ‘000d’ belongs to a block with an instruction block number ‘4’. The determination results of the information comparison unit 1904 say ‘match’ because the contents of the preliminary instruction information 1901 are an instruction ‘SUB’ and an instruction block number ‘4’. The instruction block execution count calculation unit 1905 does not calculate the execution count, but registers the present instruction ‘JNZ’ and the instruction block number ‘4’ in the preliminary instruction information 1901.

Repetition of the same procedure described above brings about provision of an instruction block execution count 1706 as shown in FIG. 24. Note that the example shown in FIG. 24 results under such premises that the condition for the conditional branch instruction in the address ‘0006’ is satisfied.

As described above, the third embodiment allows analysis of the execution count for each designated block and execution count for each instruction sequence that does not cause a branch operation to occur and does not cause convergence of the operation of that line; however, conventionally, analysis of the execution count or the like for each function and each instruction has been possible only during dynamic analysis for programs.

Frequency analysis for an executed instruction sequence conventionally has needed to search and determine all executed instruction sequences, and in the case where interruption or the like occurs, an instruction sequence for an interrupt process has been included in the same to-be-analyzed data. However, by generating to-be-analyzed data as shown in the third embodiment, searching an executable program, and counting the execution count for a target block, the same analysis results as in the case of searching all executable instruction sequences can be easily provided. As a result, the executable program size generally becomes much smaller than all executable instruction sequences, and drastic reduction in searching time is possible. Especially, this also allows effective reduction in the waiting time for an interactive process.

Fourth Embodiment

In a fourth embodiment, a case of a configurable processor design apparatus generating as an instruction set, user-defined instructions (extension instructions) that comply with user-given constraints 110 for running the program 101 is explained using a first and a second example forthwith. Moreover, an instruction subset to be used by changing part of an instruction set during execution and a corresponding processor are explained with the following third example.

FIRST EXAMPLE

FIG. 25 shows an exemplary configuration of a design apparatus according to the fourth embodiment (the first example). This design apparatus includes an instruction subset generation unit 2502, a program analysis unit 2503, an instruction set generation unit 2504, and/or related units. The instruction subset generation unit 2502 generates an instruction subset group (U_(—)0, U_(—)1, . . . , U_n) by making combinations of user-defined instructions (extension instructions) for the program 101 to be executed by the processor. The program analysis unit 2503 analyzes the effect of using each instruction subset based on syntax analysis information taken from the results of compiling the program 101 using each instruction subset, and profile information taken from the results of executing the program 101 using the compilation results. The instruction set generation unit 2504 selects an optimal instruction subset complying with the constraints 110 based on the analysis results provided by the program analysis unit 2503, and also selects the selected instruction subset as an extension instruction set definition 2505.

Firstly, a user provides to the design apparatus user-defined instruction group U and the program 101 to be executed by a processor.

In step S2502, the instruction subset generation unit 2502 combines instructions in the user-defined instruction group U provided as inputs, generating instruction subsets U_x (x=0, 1, . . . , n). Set U_all=(U_(—)0, U_(—)1, . . . , U_(—n)) donates all combinations of generated instructions.

The program analysis unit 2503 compiles and analyzes the program in the following procedure by focusing on each instruction subset U_x (x=0, 1, . . . , n) of the set U_all.

In step S2512, the program analysis unit 2503 compiles the program 101 using the instruction subset U_x as a user-defined instruction set, generating assembly codes and object codes. At this time, the compiler generates optimized assembly codes with the smallest code size using the ‘Optimization Method Used by Compiler’ technique described in the second embodiment and using user-defined instructions.

In step S2513, the program analysis unit 2503 executes through simulation the object codes generated in step S2512, and records the execution count for each basic block based on the profile information (dynamic analysis). Moreover, the program analysis unit 2503 records the number of instructions for each basic block based on the compiled program assembly codes (static analysis).

In step S2514, the program analysis unit 2503 multiplies each basic block execution count recorded in step S2513 by the number of instructions included in each basicblock, obtaining the number of the executed instructions included in each block. Using the same procedure, the number of the executed instructions included in each basic block is calculated, and the sum of each of those numbers is the number of the executed instructions included in the entire program.

In step S2515, the instruction set generation unit 2504 determines whether or not there is an instruction subset U_x that allows the number of the executed instructions calculated by the program analysis unit 2503 to satisfy the user-given constraints 110. If it is determined that there is an instruction subset U_x that satisfies the user-given constraints 110, the instruction set generation unit 2504 outputs the instruction subset U_x in which the number of the defined instructions is the smallest, as an extension instruction set definition 2505 in step S2516.

A more specific example is described next.

The program 101 written in C as shown in FIG. 26 is input to the design apparatus. This program is made up of three basic blocks. A user-defined instruction group U as shown in FIG. 27 is also input to the design apparatus.

The program analysis unit 2503 compiles the program 101 inputted in FIG. 26, into assembly codes as the compilation results.

FIG. 28 shows the result of compiling the program 101 in FIG. 26 without using the user-defined instruction group U. The assembly list in FIG. 28 is called ‘assembly list A<empty>’ here. The instructions used for assembly codes in the assembly list A<empty> are only core instructions generally available for processors.

On the other hand, FIG. 29 shows the results of assembling using the user-defined instruction group U in FIG. 27. The assembly list in FIG. 29 is called ‘assembly list A<muldivi, muldiv2>’ here. Comparison of the assembly list A<empty> with the assembly list A<muldivi, muldiv2> reveals that: lines 3 to 5 in the assembly list A<empty> have been replaced with an instruction ‘muldivi’; lines 11 to 12 have been replaced with ‘muldiv2’; and the number of instructions in the codes has thus decreased. It is also revealed that the number of to-be-executed instructions must decrease because the number of instructions has decreased.

Afterwards, the instruction set generation unit 2504 searches for an instruction subset U_x that satisfies the constraints 110 and has a minimum number of instructions. Here, a constraint such as ‘the number of executable instructions is limited to 66 or less’ is given as the constraints 110.

The number of executed instructions is calculated by finding the sum of products of the execution count for each basic block times the number of instructions in FIG. 28, revealing that the number of executed instructions included in the assembly list A<empty> is 71, which does not satisfy the constraints 110. Moreover, the number of executed instructions is calculated by finding the sum of products of the execution count for each basic block times the number of instructions in FIG. 29, revealing that the number of executed instructions included in the assembly list A<muldivi, muldiv2> is 62. This makes it clear that usage of the instructions ‘muldiv2’ and ‘muldivi’ satisfies the constraints 110.

Afterwards, the instruction set generation unit 2504 searches for a set having a minimum number of user-defined instructions. The procedure includes a given process that is repetitively executed while the constraints 110 are satisfied; where the process includes the steps of finding an instruction subset having the number of user-defined instructions reduced by one from the inputted entire set U_all and generating corresponding assembly codes.

There are three candidates for the set:

-   -   U={muldiv2, muldivi};     -   U_I={muldivi}; and     -   U_(—)2={muldiv2}

According to a more specific procedure, firstly, the instruction set generation unit 2504 derives through instruction conversion an assembly code A<muldivi> corresponding to the instruction subset U_I and an assembly code A<muldiv2> corresponding to the user-defined instruction group U_(—)2, and then determines whether or not each set satisfies the constraints 110.

FIG. 30 shows the assembly code A<muldivi> derivation results. FIG. 30 discloses that the number of executable instructions for the assembly code A<muldivi> is 69, which does not satisfy the constraints 110.

FIG. 31 shows the assembly code A<muldiv2> derivation results. FIG. 31 discloses that the number of executable instructions for the assembly code A<muldiv2> is 64, which means that the user-defined instruction group U_(—)2 satisfies the constraints 110.

Lastly, the instruction set generation unit 2504 outputs the user-defined instruction group U_(—)2 including the only instruction ‘muldiv2’ as an extension instruction set definition 2505, as exemplified in FIG. 32.

With the example described above, the only instruction set definition that satisfies the constraints 110 for the user-defined instruction group U_(—)2 and has the minimum number of user-defined instructions is provided. However, depending on what are set to the constraints 110, multiple user-defined instruction groups may satisfy the conditions for the instruction set definitions. In the case of one of the constraints 110 being, for example, ‘the number of executable instructions is 70 or less’, both the user-defined instruction group U_I and user-defined instruction group U_(—)2 satisfy that constraint. In this case, multiple instruction set definitions satisfying the condition may be output. Moreover, the order may be determined considering other conditions than what a user has designated, and outputting is made in conformity with the determined order. With the example described above, considering ‘the number of instructions in the program 101’ not designated by the user, since there are 15 instructions for the assembly code A<muldivi> corresponding to the user-defined instruction group U_I while there are 16 instructions for the assembly code A<muldiv2> corresponding to the user-defined instruction group U_(—)2, the user-defined instruction group U_I takes priority over the user-defined instruction group U_(—)2, and is then output.

SECOND EXAMPLE

With the first example, the case of using ‘the number of executed instructions in a program’ and ‘the number of instructions in a program’ as the constraints 110 is explained; however, a case of using other constraints 110 is explained with the second example.

‘Code size’ as one of the constraints 110 can be determined based on the size of an object module output as the result of assembling the program 101 using a defined instruction set.

Several methods may be considered for calculating ‘chip size’ as one of the constraints 110. According to one method, roughly estimated chip sizes for respective user-defined instructions are provided as constraints 110 by a user, and the sum thereof is given to be the chip size for a defined instruction set. Alternatively, according to a method as an application thereof, chip sizes are given for respective combinations of multiple user-defined instructions, and the sum thereof is given to be the chip size for a defined instruction set. This method is effective for the case of a single computing unit being shared by multiple user-defined instructions. Since both of the instructions ‘muldivi’ and ‘muldiv2’, for example, need a multiplier and a divider, both of these instructions are considered to share them. According to a further alternative method, a circuit for each defined instruction set is developed for using external tools such as a high-level synthesis tool, and chip size is estimated based thereon.

THIRD EXAMPLE

FIG. 33 shows an exemplary configuration of a design apparatus according to the third example of the fourth embodiment. This design apparatus operates with the following procedure. It is different from the procedure for the first example in that the instruction set generation unit 2504 is replaced with a program division unit 3302 and an instruction subset definition unit 3303, and that undefined opcodes may be included in the inputted instruction opcodes in the user-defined instruction group U.

Firstly, a user provides the design apparatus a program 101, which is to be executed by a processor, and a user-defined instruction group U. Undefined opcodes maybe included in instructions of the user-defined instruction group U.

In step S3311, the program analysis unit 3301 compiles the program 101 and generates assembly codes and object codes using provided the user-defined instruction group U. The program analysis unit 3301 also records the frequency of occurrence of each user-defined instruction in each basic block. Moreover, the program analysis unit 3301 records the execution count for each basic block based on the profile information obtained by the simulator.

In step S3312, the program division unit 3302 puts together basic blocks that employ the same user-defined instruction group U, with a basic block as a unit. Those basic blocks that employ the same user-defined instruction group are called ‘a set of instruction blocks’.

In step S3313, the instruction subset generation unit 3303 outputs as a defined instruction subset, the user-defined instruction group being used for each set of instruction blocks generated in step S3312. At this time, if the constraints 110 are given, instruction conversion is carried out with the same procedure as that of step S2516 according to the first example before outputting the defined instruction set, thereby reducing the number of user-defined instructions to be used.

In step S3314, the instruction subset generation unit 3303 determines whether or not there is an undefined opcode in instructions of the user-defined instruction group U, and if yes, an opcode is selected from an available range and assigned thereto in step S3315. The instruction subset generation unit 3303 then outputs each set of instruction blocks as a defined instruction subset 3305 in step S3316.

A more specific example is disclosed forthwith. Here, a case of providing a C language program 101 as shown in FIG. 34 and a user-defined instruction group Umax as shown in FIG. 35 is considered. As shown in FIG. 35, three instructions ‘muldivi’, ‘max3’, and ‘min3’ are defined in the user-defined instruction group Umax. These are different from those in the user-defined instruction group shown in FIG. 27 in that symbol ‘*’ is designated for opcodes. Each opcode is a bit pattern of an instruction; where a single bit is represented by a single character, and ‘0’ and ‘1’ denote bit values. ‘n’, ‘m’, and ‘k’ denote the register numbers for register operands Rn, Rm, and Rk, respectively. They are numbers obtained by encoding the values of the register numbers specified in operands of assembly codes. Note that ‘_’ is a mere delimiter, and is thus neglected as data. ‘*’ denotes an undefined item in the opcode in an instruction.

FIG. 36 shows an assembly list A<muldiv2, muldivi, max3, min3>, which is the result of assembling the program 101 in FIG. 34 by the program analysis unit 3301 using the user-defined instruction group Umax.

The program division unit 3302 divides the basic blocks 1 through 4 into sets of instruction blocks using the assembly list A<muldiv2, max3, min3>. Many division methods can be considered to be used for the operation; however, for simplicity, blocks using the same user-defined instruction are put together here, and the results are shown in FIG. 37.

Afterwards, the instruction subset generation unit 3303 generates a defined instruction subset corresponding to each set of instruction blocks. Consequently, a defined instruction subset for a set of instruction blocks IB1 is a defined instruction subset U_IB1={muldiv2}, while a defined instruction subset for a set of instruction blocks IB2 is a defined instruction subset U_IB2={min3, max3}. Since a user-defined instruction is not used for a set of instruction blocks IB3, no defined instruction subset is output.

Moreover, since there is an undefined opcode in the user-defined instruction group Umax, the instruction subset generation unit 3303 determines an opcode to be assigned. It is assumed here that an available opcode range to be the constraints 110 is given as an input. It is also assumed that ‘lower five bits are available’ is designated as an available opcode range.

As shown in FIG. 38, the fifth through eighth bits from the LSB of the opcode in each instruction are marked with ‘*’ or undefined; however, since an available range is only between the first and fifth bit, the assignment for only the fifth bit is changeable. Since only two opcodes can be designated by changing one bit, the three instructions: ‘muldiv2’, ‘max3’, and ‘min3’ cannot be assigned simultaneously. Therefore, the same opcode range is assigned to the defined instruction subsets U_IB1 and U_IB2. Since the number of user-defined instructions for each instruction subset is two or less, that assignment allows all instructions to have opcodes.

FIG. 39 shows the results of that assignment of opcodes. That assignment of opcodes to instructions may be directly designated by a user, or it may be automatically made by the instruction subset generation unit 3303.

In the case of an example shown in FIG. 39, since instructions ‘muldiv2’ and ‘max3’ may be assigned the same opcode, both of them cannot be used at the same time, and the defined instruction subset needs to be changed by a certain means. It is considered that the changing method may be a method of using dedicated instructions or a method of setting certain values to specific control registers.

FIG. 40 shows an example of a method of inserting a dedicated instruction ‘switchiss’ at the beginning of each basic block and changing over. Implementation of multiple defined instruction subsets in the same hardware, change over, and execution allows use of such instruction subsets. These defined instruction subsets may be implemented in a dynamically re-configurable circuit, for example.

As described above, according to the fourth embodiment, provision of user's requests as constraints 110 makes automatically finding instruction sets that satisfy those requests and also automatically assigning undefined opcodes possible. Moreover, assignment of multiple defined instruction subsets to the same hardware allows execution of necessary user-defined instructions and reduction of the chip size thereof.

Fifth Embodiment

With the fifth embodiment, a library optimizer, which optimizes a library to be used for compilation or the like of the program 101 based on the defined extension instructions for a configurable processor, is described.

As exemplified in FIG. 41, the library optimizer includes an analysis unit 4101, a detection unit 4104, a conversion unit 4107, and related units. The analysis unit 4101 analyzes an instruction sequence for a processor corresponding to each defined extension instruction in the extension instruction definition file 113. The detection unit 4104 determines whether or not there is said instruction sequence in the library 112 a binary codes based on the results (corresponding table 4102) of analysis by the analysis unit 4101. The binary conversion unit 4107 optimizes the library 112 a binary codes based on the detection results 4105 from the detection unit 4104.

An exemplary operation of each unit described above is detailed forthwith.

FIG. 42 shows an exemplary operation of the analysis unit 4101.

As shown in FIG. 42, the analysis unit 4101 inputs the extension instruction definition file 113 and then analyzes defined extension instructions (step S4201). The extension instruction definition file 113 may be a file generated by the design apparatus according to each embodiment described above, or a file manually made. It is assumed here that the extension instruction definition file 113 includes all defined instructions for a target processor.

The analysis unit 4101 also converts the inputted, extension instruction definition file 113 to an assembler definition file 4103 to be internally used and a C language header file 4211 or internal information equivalent to the C language header file 4211. Alternatively, the analysis unit 4101 may input from the outside, the assembler definition file 4103 and the C language header file 4211 either manually or automatically generated.

If the results of analysis in step S4201 reveal that it is an extension instruction, the analysis unit 4101 then analyzes an instruction sequence for a target processor equivalent to that extension instruction from the C language header file 4211 (step S4203). This operation uses the ‘Optimization Method Used by Compiler’ described with the second embodiment. Note that the analysis unit 4101 analyzes assembly codes other than intermediate codes.

If there is a defined instruction left in the extension instruction definition file 113, this procedure returns to step S4201, and the above mentioned process is repetitively executed until the process for all the defined instructions in the extension instruction definition file 113 has ended (step S4204).

As a result, the corresponding table 4102 showing extension instructions corresponding to respective instruction sequences for a target processor, each being able to be replaced with corresponding extension instruction, is generated as the analysis results.

At this time, only the analysis results allowing reduction of the code size are effective because there is no meaning to optimization in the case of the code size being unchanged or increased and because they are needed for local binary conversion by the conversion unit 4107. Code size information is derived from the assembler definition file 4103.

FIG. 43 shows an exemplary operation of the detection unit 4104.

As shown in FIG. 43, the detection unit 4104 searches each library 112 a for an instruction sequence possible to be converted to an extension instruction. Alternatively, all libraries may be a target in place of the library 112 a, or inputting profile information from the outside by a certain means and limiting the range of the library 112 a to be optimized and/or limiting the internal range thereof to be optimized is possible. Limitation of the range to be searched allows high-speed execution of the detection process and the conversion process. Since each library 112 a is scanned in either case, the following explanation is made under a premise that searching and converting are carried out for the independent library 112 a. A library to be subjected to detection and conversion is called a ‘target library’. It is assumed here that this target library is the library 112 a written in C. However, other languages are also accepted as long as certain conditions are satisfied. Details thereof are explained later.

A reverse-assembling result generation unit 4311 provides the results 4106 of reverse assembling the target library using the assembler definition file 4103 (step S4301). The reverse-assembling result generation unit 4311 searches the reverse-assembling results for an instruction sequence equivalent to an extension instruction using the corresponding table 4102 generated by the analysis unit 4101, and then outputs it as the searching results 4105 (step S4303). The method of searching an instruction sequence equivalent to an extension instruction uses the ‘Optimization Method Used by Compiler’ described with the second embodiment.

The process of searching an instruction sequence equivalent to an extension instruction in step S4303 cannot include converging instructions. Considering this, the reverse-assembling result generation unit 4311 attaches a certain label to converging instructions when reverse-assembling (step S4302). This allows avoidance of detecting an instruction sequence including that label as a candidate for an instruction sequence that can be replaced with an extension instruction.

The reverse-assembling result generation unit 4311 attaches that label in the following procedure.

-   (1) Attaches a certain label to the next instruction to an     unconditional branch instruction when reverse-assembling; -   (2) Calculates offset values for branch instructions in a     PC-relative addressing mode in the entire target library and     attaches a certain label thereto; and -   (3) Searches relocation information in the target library for branch     instructions in an absolute addressing mode, and attaches a certain     label thereto.

As a result, in the case of the target library being written in C, all converging instructions included in the target library have been successfully attached with labels. In the case of global symbols being referenced from other libraries or other modules, they definitely appear at the beginning of functions, and there is always an unconditional branch instruction just before each of them. In the case of the instruction just before the beginning instruction in a function not being an unconditional branch instruction with a compiler generating the target library in C language, it is technically possible to always change it to an unconditional branch instruction through use of compiler options or implementation of a corresponding process thereto in the compiler. In the case where convergence happens due to operations in a pointer addressing mode, it should be limited to being at the beginning of a function as long as it is included in libraries written in C, and it can be detected in the way as described above.

FIG. 44 shows an exemplary operation of the conversion unit 4107.

As shown in FIG. 44, the conversion unit 4107 optimizes and converts the binary codes in the library 112 a based on the results 4105 of detection by the detection unit 4104.

The conversion unit 4107 deletes all applicable instruction sequences, converts to corresponding extension instruction binary codes, and puts them in the lowest address (step S4401). After conversion, vacant regions are left as gaps.

Afterwards, the conversion unit 4107 shifts and fills the instructions after an applicable instruction sequence in corresponding gap (step S4402). At this time, the conversion unit 4107 carries out the following operation.

-   (1) In the case of an instruction to be shifted having been attached     with a label, offset values for PC-relative addressing mode branch     instructions included in the entire target library, each allowing     branching to that label but not being shifted, are corrected based     on the shifting distance of that instruction with the label, while     for direct addressing mode branch instructions, relocation     information is corrected accordingly; -   (2) In the case of an instruction to be shifted being a PC-relative     addressing mode branch instruction, if a branching-target     instruction is not shifted, the offset value for that branch     instruction is corrected based on the shifting distance; -   (3) In the case of an instruction to be shifted being a direct     addressing mode branch instruction, relocation information is     corrected accordingly; and -   (4) In the case of an instruction to be shifted being an     unconditional branch instruction (including a return instruction),     the same correction as in the case (2) or case (3) is made, that     instruction is then shifted, and shifting ends. On the other hand,     if that instruction to be shifted is not an unconditional branch     instruction, subsequent instructions are shifted in order (step     S4403).

As described above, since the aforementioned operation ends after the unconditional branch instruction has been shifted, the conversion process can be carried out at a high speed. Moreover, a newly developed gap after shifting ends may be left as is, or may be filled with an instruction ‘nop’, allowing reformed display of the reverse-assembling results provided when debugging.

Lastly, the conversion unit 4107 reassembles the target library and outputs an optimized library 112 b.

Next, a working example using a function ‘atoi’ in a standard library is explained. The function ‘atoi’ to be used here is not quite a perfect function; however, it is sufficient as a working example. It is assumed that programming is carried out using C language as shown in FIG. 45 and the binary codes for that C language program are provided as a library. Note that ‘rrrrrr’ in line 4501 of FIG. 46 denotes relocation information.

It is assumed here that a definition of extension instructions as shown in FIG. 47 is given. This definition of extension instructions may be automatically or manually generated. The library optimizer may directly input the aforementioned file, or may input an assembler definition file and a C language header file generated by a specific means as shown in FIG. 48.

The analysis unit 4101 analyzes an instruction sequence for a target processor equivalent to a defined, extension instruction from the C language header file. The ‘Optimization Method Used by Compiler’ technique described in the second embodiment is used for this analysis.

Namely, the analysis results (corresponding table 4102) revealing that an instruction sequence:

-   -   ‘slad3 $t, $n, $n’;     -   ‘mov $u, $t’;

-   ‘add3 $t, $m, −48’;     -   ‘sll $u, 1’; and

-   ‘add3 $n, $t, $u’     can be converted to an extension instruction ‘digit $n, $u’ are     provided.

The detection unit 4104 generates the reverse-assembling results 4106 for the above-mentioned binary codes. The reverse-assembling results:

-   -   ‘_atoi’;     -   ‘L50000’; and     -   ‘L5’         are labels that can be detected satisfying the conditions         detailed above, and are recognized as labels by the detection         unit 4104.

The detection unit 4104 detects, based on the analysis results, an instruction sequence that can be converted to an instruction ‘digit’ from those reverse-assembling results 4106. The ‘Optimization Method Used by Compiler’ technique described in the second embodiment is used for this analysis.

As a result, the detection results 4105 revealing that an instruction sequence:

-   -   ‘slad3 $0, $0, $0’;     -   ‘mov $12, $0’;

-   ‘add3 $0, $11, −48’;     -   ‘sll $12, 1’; and

-   ‘add3 $0, $0, $12’     can be converted to an extension instruction ‘digit $0, $11’ are     output.

The conversion unit 4107 has the detected sequence of codes as a gap, and converts the top of the gap to an extension instruction. At this time, the target library shown in FIG. 49 is provided. The unprocessed gap (lines 4811 and 4813) is shown with ‘xxxx’.

Afterwards, the conversion unit 4107 starts shifting for filling the gap. To delete ‘xxxx’ indicating the gap, the instruction sequence just after the gap is shifted. Since a label ‘L5’ (line 4815) is shifted, the binary codes for an instruction (instruction ‘beqz’ (line 4809)) using an offset pointing at that label are also converted. Moreover, since a PC-relative addressing mode branch instruction (instruction ‘bra’ (line 4814)) is also shifted, the binary codes thereof are converted. Since an instruction ‘ret’ (line 4816) is an unconditional branch instruction, shifting ends at the time when it has been shifted. The shifting results are shown in FIG. 50.

A newly developed gap (lines 4914 to 4917) may be left as is; however, as shown in FIG. 51, it is filled with an instruction ‘nop’ so as to enhance the appearance of the reverse-assembling results provided during debugging.

As described above, according to the fifth embodiment, a library linked to an application program may be optimized using extension instructions, allowing generation of a high-speed executable object file.

While the embodiments according to the present invention have been detailed, the present invention can be implemented with a variety of configurations without deviating from the spirit and the main characteristics of the present invention.

Therefore, since each embodiment described above is a mere example from every aspect, the scope of the present invention should not be interpreted in a restricted manner. The scope of the present invention is defined by the claims, and is not limited by the contents of the specification according to the present invention. Moreover, all modifications and/or changes belonging to items within the scope of the claims or equivalents thereto have to fall within the scope of the present invention.

The present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the present invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. 

1. A design apparatus for designing a configurable processor for an application, comprising: an analysis unit configured to analyze the content of a program to be executed by the processor; a hardware extension unit configured to search the program for a part of the program allowing hardware extension in accordance with the analysis results by the analysis unit and generates hardware extension information for the searched part; an extension instruction definition unit configured to search the program for a part of the program allowing use of an extension instruction in accordance with the analysis results by the analysis unit and generates definition of an extension instruction for the searched part; and a performance estimation unit configured to estimate whether the performance of the processor satisfies a target performance using at least one of the hardware extension information generated by the hardware extension unit and the definition of the extension instruction generated by the extension instruction definition unit; and wherein the analysis unit includes at least one of a static analysis unit configured to analyze static analysis information using syntax analysis information obtained from the results of compiling the program, and a dynamic analysis unit configured to analyze dynamic analysis information using profile information obtained from the results of executing the program.
 2. The design apparatus according to claim 1, further comprising an inputting unit configured to input constraints for limiting the hardware extension and the use of an extension instruction, wherein the hardware extension unit carries out hardware extension while satisfying the constraints, and the extension instruction definition unit implements an extension instruction while satisfying the constraints.
 3. The design apparatus according to claim 1, further comprising an inputting unit configured to input at least one of designative information that designates a part of the program allowing hardware extension, designative information to designate a part of the program allowing use of an extension instruction, designative information to designate a part of the program not allowing hardware extension, and designative information to designate a part of the program not allowing use of an extension instruction.
 4. A design apparatus for designing a configurable processor for an application, comprising: a dynamic analysis unit configured to analyze dynamic analysis information using profile information obtained from the results of executing a program to be executed by the processor, the dynamic analysis unit comprises an instruction sequence division unit configured to divide an instruction sequence in the program into blocks and an instruction execution unit configured to count how many instructions are executed in each divided block, and the dynamic analysis unit outputs the resulting executed instruction count for each divided block as a dynamic analysis result; a hardware extension unit configured to search the program for a part of the program allowing hardware extension by estimating an execution speed in accordance with the dynamic analysis results by the dynamic analysis unit and generate hardware extension information for the searched part if the estimated execution speed does not satisfy a predetermined target performance; and an extension instruction definition unit configured to search the program for a part of the program allowing use of an extension instruction by estimating an execution speed in accordance with the dynamic analysis results by the dynamic analysis unit and generate definition of an extension instruction for the searched part if the estimated execution speed does not satisfy a predetermined target performance; and wherein the instruction sequence division unit divides an instruction sequence in the program into blocks so that each single block is an instruction sequence not including branch instructions and not resulting in convergence.
 5. The design apparatus according to claim 4, wherein the instruction execution unit counts how many times each starting instruction in each block made up of the instruction sequence groups not including branch instructions and not resulting in convergence are executed, thereby providing the resulting block execution counts.
 6. A computer-aided design method of designing a configurable processor for an application and satisfying a target performance for the processor, comprising: analyzing, by an analysis unit, the content of a program to be executed by the processor; searching, by a hardware extension unit, the program for a part of the program allowing hardware extension in accordance with the analysis results by the analysis unit and generating hardware extension information of the searched part; searching, by an extension instruction definition unit, the program for a part of the program allowing use of an extension instruction in accordance with the analysis results by the analysis unit and generating a definition of an extension instruction for the searched part; and estimating, by a performance estimation unit, whether the performance of the processor satisfies a target performance when using at least one of the hardware extension information generated by the hardware extension unit and the definition of the extension instruction generated by the extension instruction definition unit; and wherein the analyzing includes at least one of a static analyzing, by a static analysis unit, to analyze static analysis information using syntax analysis information obtained from the results of compiling the program, and a dynamic analyzing, by a dynamic analysis unit, to analyze dynamic analysis information using profile information obtained from the results of executing the program.
 7. A computer-aided design method of designing a configurable processor for an application, comprising: dividing, by an instruction sequence division unit, an instruction sequence of a program to be executed by the processor into blocks; executing, by a dynamic analysis unit, the program, counting, by instruction execution unit, how many instructions in each divided block are executed, and outputting, by the dynamic analysis unit, the resulting execution count as dynamic analysis results; searching, by a hardware extension unit, the program for a part of the program allowing hardware extension in accordance with the dynamic analysis results and generating hardware extension information of the searched part if the estimated execution speed does not satisfy a predetermined target performance; and searching, by an extension instruction definition unit, the program for a part of the program allowing use of an extension instruction in accordance with the dynamic analysis results and generating definition of an extension instruction for the searched part if the estimated execution speed does not satisfy a predetermined target performance; and wherein the instruction sequence division unit divides an instruction sequence in the program into blocks so that each single block is an instruction sequence not including branch instructions and not resulting in convergence.
 8. A design method satisfying a target performance for a processor which is re-configurable for an application, comprising: inputting a program to be executed by the processor and analyzing the content of the inputted program; searching the program for a part of the program allowing hardware extension in accordance with the analysis results and generating hardware extension information of the searched part; searching the program for a part allowing use of an extension instruction in accordance with the analysis results and generating definition of an extension instruction for the searched part; and estimating, based on at least one of the generated definition of the extension instruction and the generated hardware extension information, whether the performance of the processor satisfies a target performance; and wherein the analyzing includes at least one of analyzing static analysis information using syntax analysis information obtained from the results of compiling the program, and analyzing dynamic analysis information using profile information obtained from the results of executing the program.
 9. The method, according to claim 8, wherein a plurality of definitions for instruction subsets are implemented in the same hardware, and the plurality of implemented definitions of instruction subsets are changed over during execution.
 10. A fabrication method of a semiconductor device having a configurable processor which is re-configurable for an application, comprising: analyzing the content of a program to be executed by the processor; searching the program for a part of the program allowing hardware extension in accordance with the analysis results and generating hardware extension information of the searched part; searching the program for a part of the program allowing use of an extension instruction in accordance with the analysis results and generating a definition of an extension instruction for the searched part; estimating whether the performance of the processor satisfies a target performance when using at least one of the generated hardware extension information and the generated definition of the extension instruction; generating mask data of a circuit pattern of a semiconductor circuit including the processor; generating masks from the generated mask data; and forming the circuit pattern in or on a semiconductor substrate using the generated masks; and wherein the analyzing includes at least one of analyzing static analysis information using syntax analysis information obtained from the results of compiling the program, and analyzing dynamic analysis information using profile information obtained from the results of executing the program. 